build(codeql): enabling code scanning #16
Conversation
|
This pull request sets up GitHub code scanning for this repository. Once the scans have completed and the checks have passed, the analysis results for this pull request branch will appear on this overview. Once you merge this pull request, the 'Security' tab will show more code scanning analysis results (for example, for the default branch). Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results. For more information about GitHub code scanning, check out the documentation. |
|
Let's put this on hold, until we finalize the proper configuration/approach in xlts-dev/angularjs-webpack-babel#29. |
jzolnowski
force-pushed
the
enabling-code-scanning
branch
from
46457ab to
d505612
Compare
We can use CodeQL to identify vulnerabilities and errors in our JavaScript code and display the results as code scanning alerts on GitHub
jzolnowski
force-pushed
the
enabling-code-scanning
branch
from
ef55ef5 to
3216297
Compare
There was a problem hiding this comment.
Code scanning found an issue: https://github.com/xlts-dev/angularjs-ionic-v1/security/code-scanning/1
It is a false positive, but maybe we could refactor the code to avoid triggering the warning.
Otherwise, the PR lgtm 👍
jzolnowski
force-pushed
the
enabling-code-scanning
branch
from
c553c97 to
5641097
Compare
… the first occurrence of '>'
jzolnowski
force-pushed
the
enabling-code-scanning
branch
from
5641097 to
732d4f6
Compare
3 participants
We can use CodeQL to identify vulnerabilities and errors in our JavaScript code and display the results as code scanning alerts on GitHub